System and method for improving cache performance

ABSTRACT

A method, computer program product, and computing system for receiving a write request on a first cache system, wherein the write request identifies new content to be written to a data array. A write request content identifier associated with the new content is compared to a plurality of content identifiers included within a content directory for the first cache system to determine if a matching content identifier exists. Each of the plurality of content identifiers is associated with a piece of previously-written content included within the first cache system. If a matching content identifier is identified, content on the data array is copied from a first location on the data array associated with the matching content identifier to a second location on the data array associated with the write request content identifier.

TECHNICAL FIELD

This disclosure relates to cache memory systems and, more particularly,to systems and methods for improving the performance of cache memorysystems.

BACKGROUND

Storing and safeguarding electronic content is of paramount importancein modern business. Accordingly, various systems may be employed toprotect such electronic content.

The use of solid-state storage devices is increasing in popularity. Asolid state storage device is a content storage device that usessolid-state memory to store persistent content. A solid-state storagedevice may emulate (and therefore replace) a conventional hard diskdrive. Additionally/alternatively, a solid state storage device may beused within a cache memory system. With no moving parts, a solid-statestorage device largely eliminates (or greatly reduces) seek time,latency and other electromechanical delays and failures associated witha conventional hard disk drive.

SUMMARY OF DISCLOSURE

In a first implementation, a computer-implemented method of processingwrite requests includes receiving a write request on a first cachesystem, wherein the write request identifies new content to be writtento a data array. A write request content identifier associated with thenew content is compared to a plurality of content identifiers includedwithin a content directory for the first cache system to determine if amatching content identifier exists. Each of the plurality of contentidentifiers is associated with a piece of previously-written contentincluded within the first cache system. If a matching content identifieris identified, content on the data array is copied from a first locationon the data array associated with the matching content identifier to asecond location on the data array associated with the write requestcontent identifier.

One or more of the following features may be included. If a matchingcontent identifier is not identified: the new content may be written tothe first cache system; the content directory may be modified to includethe write request content identifier; and the new content may beprovided to the data array. The write request content identifier may begenerated for the new content. The write request content identifier maybe a hash function of the new content to be written to the data array.The write request may identify a logical unit and a storage address forstoring the new content within the data array.

If a matching content identifier is identified, an entry within thecontent directory that is associated with the matching contentidentifier may be modified to identify the logical storage unit and thestorage address for storing the new content within the data array. Thecontent directory for the first cache system may include a plurality ofentries, wherein each of the plurality of entries is associated with aspecific piece of previously-written content within the first cachesystem. Each of the plurality of entries within the content directorymay identify: a logical storage unit and a storage address at which thespecific piece of previously-written content is located within thestorage array; a first cache address at which the specific piece ofpreviously-written content is located within the first cache system, anda content identifier for the specific piece of previously-writtencontent.

In another implementation, a computer program product resides on acomputer readable medium that has a plurality of instructions stored onit. When executed by a processor, the instructions cause the processorto perform operations including receiving a write request on a firstcache system, wherein the write request identifies new content to bewritten to a data array. A write request content identifier associatedwith the new content is compared to a plurality of content identifiersincluded within a content directory for the first cache system todetermine if a matching content identifier exists. Each of the pluralityof content identifiers is associated with a piece of previously-writtencontent included within the first cache system. If a matching contentidentifier is identified, content on the data array is copied from afirst location on the data array associated with the matching contentidentifier to a second location on the data array associated with thewrite request content identifier.

One or more of the following features may be included. If a matchingcontent identifier is not identified: the new content may be written tothe first cache system; the content directory may be modified to includethe write request content identifier; and the new content may beprovided to the data array. The write request content identifier may begenerated for the new content. The write request content identifier maybe a hash function of the new content to be written to the data array.The write request may identify a logical unit and a storage address forstoring the new content within the data array.

If a matching content identifier is identified, an entry within thecontent directory that is associated with the matching contentidentifier may be modified to identify the logical storage unit and thestorage address for storing the new content within the data array. Thecontent directory for the first cache system may include a plurality ofentries, wherein each of the plurality of entries is associated with aspecific piece of previously-written content within the first cachesystem. Each of the plurality of entries within the content directorymay identify: a logical storage unit and a storage address at which thespecific piece of previously-written content is located within thestorage array; a first cache address at which the specific piece ofpreviously-written content is located within the first cache system, anda content identifier for the specific piece of previously-writtencontent.

In another implementation, a computing system includes at least oneprocessor and at least one memory architecture coupled with the at leastone processor, wherein the computing system is configured to performoperations including receiving a write request on a first cache system,wherein the write request identifies new content to be written to a dataarray. A write request content identifier associated with the newcontent is compared to a plurality of content identifiers includedwithin a content directory for the first cache system to determine if amatching content identifier exists. Each of the plurality of contentidentifiers is associated with a piece of previously-written contentincluded within the first cache system. If a matching content identifieris identified, content on the data array is copied from a first locationon the data array associated with the matching content identifier to asecond location on the data array associated with the write requestcontent identifier.

One or more of the following features may be included. If a matchingcontent identifier is not identified: the new content may be written tothe first cache system; the content directory may be modified to includethe write request content identifier; and the new content may beprovided to the data array. The write request content identifier may begenerated for the new content. The write request content identifier maybe a hash function of the new content to be written to the data array.The write request may identify a logical unit and a storage address forstoring the new content within the data array.

If a matching content identifier is identified, an entry within thecontent directory that is associated with the matching contentidentifier may be modified to identify the logical storage unit and thestorage address for storing the new content within the data array. Thecontent directory for the first cache system may include a plurality ofentries, wherein each of the plurality of entries is associated with aspecific piece of previously-written content within the first cachesystem. Each of the plurality of entries within the content directorymay identify: a logical storage unit and a storage address at which thespecific piece of previously-written content is located within thestorage array; a first cache address at which the specific piece ofpreviously-written content is located within the first cache system, anda content identifier for the specific piece of previously-writtencontent.

The details of one or more implementations are set forth in theaccompanying drawings and the description below. Other features andadvantages will become apparent from the description, the drawings, andthe claims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagrammatic view of a storage system and a data cachingprocess coupled to a distributed computing network;

FIG. 2 is a diagrammatic view of the storage system of FIG. 1;

FIG. 3 is a diagrammatic view of a data write request for use with thedata caching process of FIG. 1;

FIG. 4 is a diagrammatic view of a data read request for use with thedata caching process of FIG. 1;

FIG. 5 is a diagrammatic view of a content directory for use with thedata caching process of FIG. 1;

FIG. 6 is a first flow chart of the data caching process of FIG. 1;

FIG. 7 is a second flow chart of the data caching process of FIG. 1;

FIG. 8 is a third flow chart of the data caching process of FIG. 1;

FIG. 9 is a fourth flow chart of the data caching process of FIG. 1; and

FIG. 10 is a fifth flow chart of the data caching process of FIG. 1.

Like reference symbols in the various drawings indicate like elements.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

System Overview:

As will be appreciated by one skilled in the art, the present disclosuremay be embodied as a method, system, or computer program product.Accordingly, the present disclosure may take the form of an entirelyhardware embodiment, an entirely software embodiment (includingfirmware, resident software, micro-code, etc.) or an embodimentcombining software and hardware aspects that may all generally bereferred to herein as a “circuit,” “module” or “system.” Furthermore,the present disclosure may take the form of a computer program producton a computer-usable storage medium having computer-usable program codeembodied in the medium.

Any suitable computer usable or computer readable medium may beutilized. The computer-usable or computer-readable medium may be, forexample but not limited to, an electronic, magnetic, optical,electromagnetic, infrared, or semiconductor system, apparatus, device,or propagation medium. More specific examples (a non-exhaustive list) ofthe computer-readable medium would include the following: an electricalconnection having one or more wires, a portable computer diskette, ahard disk, a random access memory (RAM), a read-only memory (ROM), anerasable programmable read-only memory (EPROM or Flash memory), anoptical fiber, a portable compact disc read-only memory (CD-ROM), anoptical storage device, a transmission media such as those supportingthe Internet or an intranet, or a magnetic storage device. Note that thecomputer-usable or computer-readable medium could even be paper oranother suitable medium upon which the program is printed, as theprogram can be electronically captured, via, for instance, opticalscanning of the paper or other medium, then compiled, interpreted, orotherwise processed in a suitable manner, if necessary, and then storedin a computer memory. In the context of this document, a computer-usableor computer-readable medium may be any medium that can contain, store,communicate, propagate, or transport the program for use by or inconnection with the instruction execution system, apparatus, or device.The computer-usable medium may include a propagated data signal with thecomputer-usable program code embodied therewith, either in baseband oras part of a carrier wave. The computer usable program code may betransmitted using any appropriate medium, including but not limited tothe Internet, wireline, optical fiber cable, RF, etc.

Computer program code for carrying out operations of the presentdisclosure may be written in an object oriented programming languagesuch as Java, Smalltalk, C++ or the like. However, the computer programcode for carrying out operations of the present disclosure may also bewritten in conventional procedural programming languages, such as the“C” programming language or similar programming languages. The programcode may execute entirely on the user's computer, partly on the user'scomputer, as a stand-alone software package, partly on the user'scomputer and partly on a remote computer or entirely on the remotecomputer or server. In the latter scenario, the remote computer may beconnected to the user's computer through a local area network (LAN) or awide area network (WAN), or the connection may be made to an externalcomputer (for example, through the Internet using an Internet ServiceProvider).

The present disclosure is described below with reference to flowchartillustrations and/or block diagrams of methods, apparatus (systems) andcomputer program products according to embodiments of the disclosure. Itwill be understood that each block of the flowchart illustrations and/orblock diagrams, and combinations of blocks in the flowchartillustrations and/or block diagrams, can be implemented by computerprogram instructions. These computer program instructions may beprovided to a processor of a general purpose computer, special purposecomputer, or other programmable data processing apparatus to produce amachine, such that the instructions, which execute via the processor ofthe computer or other programmable data processing apparatus, createmeans for implementing the functions/acts specified in the flowchartand/or block diagram block or blocks.

These computer program instructions may also be stored in acomputer-readable memory that can direct a computer or otherprogrammable data processing apparatus to function in a particularmanner, such that the instructions stored in the computer-readablememory produce an article of manufacture including instruction meanswhich implement the function/act specified in the flowchart and/or blockdiagram block or blocks.

The computer program instructions may also be loaded onto a computer orother programmable data processing apparatus to cause a series ofoperational steps to be performed on the computer or other programmableapparatus to produce a computer implemented process such that theinstructions which execute on the computer or other programmableapparatus provide steps for implementing the functions/acts specified inthe flowchart and/or block diagram block or blocks.

System Overview:

Referring to FIG. 1, there is shown data caching process 10 that mayreside on and may be executed by storage system 12, which may beconnected to network 14 (e.g., the Internet or a local area network).Examples of storage system 12 may include, but are not limited to: aNetwork Attached Storage (NAS) system, a Storage Area Network (SAN), apersonal computer with a memory system, a server computer with a memorysystem, and a cloud-based device with a memory system.

As is known in the art, a SAN may include one or more of a personalcomputer, a server computer, a series of server computers, a minicomputer, a mainframe computer, a RAID device and a NAS system. Thevarious components of storage system 12 may execute one or moreoperating systems, examples of which may include but are not limited to:Microsoft Windows XP Server™; Novell Netware™; Redhat Linux™, Unix, or acustom operating system, for example.

The instruction sets and subroutines of data caching process 10, whichmay be stored on storage device 16 included within storage system 12,may be executed by one or more processors (not shown) and one or morememory architectures (not shown) included within storage system 12.Storage device 16 may include but is not limited to: a hard disk drive;a tape drive; an optical drive; a RAID device; a random access memory(RAM); a read-only memory (ROM); and all forms of flash memory storagedevices.

Network 14 may be connected to one or more secondary networks (e.g.,network 18), examples of which may include but are not limited to: alocal area network; a wide area network; or an intranet, for example.

Various data requests (e.g. data request 20) may be sent from clientapplications 22, 24, 26, 28 to storage system 12. Examples of datarequest 20 may include but are not limited to data write requests (i.e.a request that content be written to storage system 12) and data readrequests (i.e. a request that content be read from storage system 12).

The instruction sets and subroutines of client applications 22, 24, 26,28, which may be stored on storage devices 30, 32, 34, 36 (respectively)coupled to client electronic devices 38, 40, 42, 44 (respectively), maybe executed by one or more processors (not shown) and one or more memoryarchitectures (not shown) incorporated into client electronic devices38, 40, 42, 44 (respectively). Storage devices 30, 32, 34, 36 mayinclude but are not limited to: hard disk drives; tape drives; opticaldrives; RAID devices; random access memories (RAM); read-only memories(ROM), and all forms of flash memory storage devices. Examples of clientelectronic devices 38, 40, 42, 44 may include, but are not limited to,personal computer 38, laptop computer 40, personal digital assistant 42,notebook computer 44, a server (not shown), a data-enabled, cellulartelephone (not shown), and a dedicated network device (not shown).

Users 46, 48, 50, 52 may access storage system 12 directly throughnetwork 14 or through secondary network 18. Further, storage system 12may be connected to network 14 through secondary network 18, asillustrated with link line 54.

The various client electronic devices may be directly or indirectlycoupled to network 14 (or network 18). For example, personal computer 38is shown directly coupled to network 14 via a hardwired networkconnection. Further, notebook computer 44 is shown directly coupled tonetwork 18 via a hardwired network connection. Laptop computer 40 isshown wirelessly coupled to network 14 via wireless communicationchannel 56 established between laptop computer 40 and wireless accesspoint (i.e., WAP) 58, which is shown directly coupled to network 14. WAP58 may be, for example, an IEEE 802.11a, 802.11b, 802.11g, 802.11n,Wi-Fi, and/or Bluetooth device that is capable of establishing wirelesscommunication channel 56 between laptop computer 40 and WAP 58. Personaldigital assistant 42 is shown wirelessly coupled to network 14 viawireless communication channel 60 established between personal digitalassistant 42 and cellular network/bridge 62, which is shown directlycoupled to network 14.

As is known in the art, all of the IEEE 802.11x specifications may useEthernet protocol and carrier sense multiple access with collisionavoidance (i.e., CSMA/CA) for path sharing. The various 802.11xspecifications may use phase-shift keying (i.e., PSK) modulation orcomplementary code keying (i.e., CCK) modulation, for example. As isknown in the art, Bluetooth is a telecommunications industryspecification that allows e.g., mobile phones, computers, and personaldigital assistants to be interconnected using a short-range wirelessconnection.

Client electronic devices 38, 40, 42, 44 may each execute an operatingsystem, examples of which may include but are not limited to MicrosoftWindows™, Microsoft Windows CE™, Redhat Linux™, or a custom operatingsystem.

The Data Caching Process:

For the following discussion, client application 22 is going to bedescribed for illustrative purposes. However, this is not intended to bea limitation of this disclosure, as other client applications (e.g.,client applications 24, 26, 28) may be equally utilized.

For illustrative purposes, storage system 12 will be described as beinga network-based storage system that includes a plurality ofelectro-mechanical backend storage devices. However, this is forillustrative purposes only and is not intended to be a limitation ofthis disclosure, as other configurations are possible and are consideredto be within the scope of this disclosure. For example and as discussedabove, storage system 12 may be a personal computer that includes asingle electro-mechanical storage device.

Referring also to FIG. 2, storage system 12 may include a servercomputer/controller (e.g. server computer/controller 100), and aplurality of storage targets T_(1-n) (e.g. storage targets 102, 104,106, 108). Storage targets 102, 104, 106, 108 may be configured toprovide various levels of performance and/or high availability. Forexample, one or more of storage targets 102, 104, 106, 108 may beconfigured as a RAID 0 array, in which data is striped across storagetargets. By striping data across a plurality of storage targets,improved performance may be realized. However, RAID 0 arrays do notprovide a level of high availability. Accordingly, one or more ofstorage targets 102, 104, 106, 108 may be configured as a RAID 1 array,in which data is mirrored between storage targets. By mirroring databetween storage targets, a level of high availability is achieved asmultiple copies of the data are stored within storage system 12.

While storage targets 102, 104, 106, 108 are discussed above as beingconfigured in a RAID 0 or RAID 1 array, this is for illustrativepurposes only and is not intended to be a limitation of this disclosure,as other configurations are possible. For example, storage targets 102,104, 106, 108 may be configured as a RAID 3, RAID 4, RAID 5 or RAID 6array.

While in this particular example, storage system 12 is shown to includefour storage targets (e.g. storage targets 102, 104, 106, 108), this isfor illustrative purposes only and is not intended to be a limitation ofthis disclosure. Specifically, the actual number of storage targets maybe increased or decreased depending upon e.g. the level ofredundancy/performance/capacity required.

Storage system 12 may also include one or more coded targets 110. As isknown in the art, a coded target may be used to store coded data thatmay allow for the regeneration of data lost/corrupted on one or more ofstorage targets 102, 104, 106, 108. An example of such a coded targetmay include but is not limited to a hard disk drive that is used tostore parity data within a RAID array.

While in this particular example, storage system 12 is shown to includeone coded target (e.g., coded target 110), this is for illustrativepurposes only and is not intended to be a limitation of this disclosure.Specifically, the actual number of coded targets may be increased ordecreased depending upon e.g. the level ofredundancy/performance/capacity required.

Examples of storage targets 102, 104, 106, 108 and coded target 110 mayinclude one or more electro-mechanical hard disk drives, wherein acombination of storage targets 102, 104, 106, 108 and coded target 110may form non-volatile, electro-mechanical memory system 112.

The manner in which storage system 12 is implemented may vary dependingupon e.g. the level of redundancy/performance/capacity required. Forexample, storage system 12 may be a RAID device in which servercomputer/controller 100 is a RAID controller card and storage targets102, 104, 106, 108 and/or coded target 110 are individual“hot-swappable” hard disk drives. An example of such a RAID device mayinclude but is not limited to an NAS device. Alternatively, storagesystem 12 may be configured as a SAN, in which servercomputer/controller 100 may be e.g., a server computer and each ofstorage targets 102, 104, 106, 108 and/or coded target 110 may be a RAIDdevice and/or computer-based hard disk drive. Further still, one or moreof storage targets 102, 104, 106, 108 and/or coded target 110 may be aSAN.

In the event that storage system 12 is configured as a SAN, the variouscomponents of storage system 12 (e.g. server computer/controller 100,storage targets 102, 104, 106, 108, and coded target 110) may be coupledusing network infrastructure 114, examples of which may include but arenot limited to an Ethernet (e.g., Layer 2 or Layer 3) network, a fiberchannel network, an InfiniBand network, or any other circuitswitched/packet switched network.

Storage system 12 may execute all or a portion of data caching process10. The instruction sets and subroutines of data caching process 10,which may be stored on a storage device (e.g., storage device 16)coupled to server computer/controller 100, may be executed by one ormore processors (not shown) and one or more memory architectures (notshown) included within server computer/controller 100. Storage device 16may include but is not limited to: a hard disk drive; a tape drive; anoptical drive; a RAID device; a random access memory (RAM); a read-onlymemory (ROM); and all forms of flash memory storage devices.

As discussed above, various data requests (e.g. data request 20) may begenerated. For example, these data requests may be sent from clientapplications 22, 24, 26, 28 to storage system 12.Additionally/alternatively and when server computer/controller 100 isconfigured as an application server, these data requests may beinternally generated within server computer/controller 100. Examples ofdata request 20 may include but are not limited to data write request116 (i.e. a request that content 118 be written to storage system 12)and data read request 120 (i.e. a request that content 118 be read fromstorage system 12).

Server computer/controller 100 may include input-output logic 122 (e.g.,a network interface card), processing logic 124, and first cache system126. Examples of first cache system 126 may include but are not limitedto a volatile, solid-state, cache memory system (e.g., a dynamic RAMcache memory system) and/or a non-volatile, solid-state, cache memorysystem (e.g., a flash-based, cache memory system).

During operation of server computer/controller 100, content 118 to bewritten to storage system 12 may be received by input-output logic 122(e.g. from network 14 and/or network 18) and processed by processinglogic 124. Additionally/alternatively and when servercomputer/controller 100 is configured as an application server, content118 to be written to storage system 12 may be internally generated byserver computer/controller 100. As will be discussed below in greaterdetail, processing logic 124 may initially store content 118 withinfirst cache system 126.

Depending on the manner in which first cache system 126 is configured,processing logic 124 may immediately write content 118 to second cachesystem 128/non-volatile, electro-mechanical memory system 112 (if firstcache system 126 is configured as a write-through cache) or maysubsequently destage content 118 to second cache system128/non-volatile, electro-mechanical memory system 112 (if first cachesystem 126 is configured as a write-back cache). Additionally and incertain configurations, processing logic 124 may calculate and storecoded data on coded target 110 (included within non-volatile,electromechanical memory system 112) that may allow for the regenerationof data lost/corrupted on one or more of storage targets 102, 104, 106,108. For example, if processing logic 124 was included within a RAIDcontroller card or a NAS/SAN controller, processing logic 124 maycalculate and store coded data on coded target 110. However, ifprocessing logic 124 was included within e.g., an applications server,data array 130 may calculate and store coded data on coded target 110.

The combination of second cache system 128 and non-volatile,electromechanical memory system 112 may form data array 130, whereinfirst cache system 126 may be sized so that the number of times thatdata array 130 is accessed may be reduced. Accordingly, by sizing firstcache system 126 so that first cache system 126 retains a quantity ofdata sufficient to satisfy a significant quantity of data requests(e.g., data request 20), the overall performance of storage system 12may be enhanced. As will be described below in greater detail, firstcache system 126 may be a content-aware cache system.

Further, second cache system 128 within data array 130 may be sized sothat the number of times that non-volatile, electromechanical memorysystem 112 is accessed may be reduced. Accordingly, by sizing secondcache system 128 so that second cache system 128 retains a quantity ofdata sufficient to satisfy a significant quantity of data requests(e.g., data request 20), the overall performance of storage system 12may be enhanced. As will be described below in greater detail, secondcache system 130 may be a content-aware cache system.

As discussed above, the instruction sets and subroutines of data cachingprocess 10, which may be stored on storage device 16 included withinstorage system 12, may be executed by one or more processors (not shown)and one or more memory architectures (not shown) included within storagesystem 12. Accordingly, in addition to being executed on servercomputer/controller 100, some or all of the instruction sets andsubroutines of data caching process 10 may be executed by one or moreprocessors (not shown) and one or more memory architectures (not shown)included within data array 130.

Referring also to FIGS. 3-4, data request 20 (e.g. data read request 116and/or data write request 120) may be processed by servercomputer/controller 100 to extract pertinent information concerningthese data requests.

When data request 20 is a data write request (e.g., write request 116),write request 116 may include content 118 to be written to data array130. Additionally, write request 116 may include a storage address 200that defines the intended storage location within storage array 130 atwhich content 118 is to be stored. For example, storage address 200 maydefine a particular logical unit within data array 130 (e.g., a LUN orLogical Unit Number) and a particular storage address within thatspecific logical unit (e.g., an LBA or Logical Block Address) forstoring content 118.

Concerning read request 120, these requests do not include any contentto be written to data array 130, as these are read requests and concerncontent to be read from data array 130. Read request 120 may include astorage address 202 that defines the storage location within storagearray 130 from which content is to be retrieved. For example, storageaddress 202 may define a particular logical unit within data array 130(e.g., a LUN or Logical Unit Number) and a particular storage addresswithin that specific logical unit (e.g., an LBA or Logical BlockAddress) for retrieving the content sought from data array 130.

As will be discussed below in greater detail and referring also to FIG.5, data caching process 10 may maintain content directory 250, which maybe used to locate various pieces of content within first cache system126. In one particular embodiment of content directory 250, contentdirectory 250 may include plurality of entries 252, wherein each ofthese entries may identify: data array storage address 200/202 (e.g. alogical storage unit and a storage address at which a specific piece ofpreviously-written content is located within storage array 130); firstcache address 254 (e.g., the location within first cache system 126 atwhich the specific piece of previously-written content is also located),and content identifier 256 for the specific piece of previously-writtencontent. Accordingly, content directory 250 may identify the location ofspecific pieces of content included within first cache system 126 andtheir corresponding pieces of data within data array 130, as well as acontent identifier that uniquely identifies the specific piece ofcontent.

Content identifier 256 may be a mathematical representation of thespecific piece of previously-written content that may allow e.g. servercomputer/controller 100 to quickly determine whether two pieces ofpreviously-written content are identical, as identical pieces of contentwould have identical content identifiers. In one particular embodiment,content identifier 256 may be a hash function (e.g., a cryptographichash) of the previously-written content.

Compression Ratio Monitoring:

Data caching process 10 may be configured to compress the data stored ondata array 130 to conserve storage space if computationally desirable.

Referring also to FIG. 6, data caching process 10 may be configured toreceive 300 read request 120 on first cache system 126, wherein readrequest 120 identifies previously-written content (as defined by storageaddress 202) included within data array 130. For example, assume thatuser 46 is using client application 22 to access data (i.e. content 132)that is currently being stored on data array 130. Accordingly, clientapplication 22 may generate read request 120 which, as discussed above,may define a particular logical unit within data array 130 (e.g., a LUNor Logical Unit Number) and a particular storage address within thatspecific logical unit (e.g., an LBA or Logical Block Address) forretrieving content 132 sought from data array 130 by client application22.

Assume that read request 120 defines LUN0/LBA5 as the location ofcontent 132 within data array 130. Upon receiving 300 read request 120,data caching process 10 may compare the location of content 132 withindata array 130 (namely LUN0/LBA5) with each of the plurality of entries252 defined within content directory 250 to determine if a copy ofcontent 132 is locally available (i.e., cached) within first cachesystem 126. If LUN0/LBA5 was defined within content directory 250(meaning that a local cached copy of content 132 is present/availablewithin first cache system 126), that particular entry would also definea corresponding first cache address (e.g. first cache address 254)within first cache system 126 at which content 132 would belocally-available and retrievable from the first cache system 126.Conversely, in the event that LUN0/LBA5 is not defined within contentdirectory 250 (meaning that a local cached copy of content 132 is notpresent/available within first cache system 126), data caching process10 may need to obtain 302 content 132 identified in read request 120from data array 130. In this particular example, since LUN0/LBA5 is notdefined within content directory 250, a local cached copy of content 132is not present/available within first cache system 126 and data cachingprocess 10 will be need to obtain 302 content 132 from data array 130.

Once content 132 is obtained 302 by data caching process 10, datacaching process 10 may compress 304 content 132 prior to content 132being stored within first cache system 126, thus generating compressedcontent 134 which may be stored within (and conserve the storage spaceof) first cache system 126. When compressing 304 content 132 to generatecompressed content 134, data caching process 10 may determine 306compression ratio 136 for compressed content 134. For example, ifcontent 132 is 1.00 MB in size and compressed content 134 is 200 kB insize, data caching process 10 may determine 306 compression ratio 136 of5:1 for compressed content 134. Data caching process 10 may provide 308compression ratio 136 to data array 130.

Upon receiving compression ratio 136, data caching process 10 maycompare compression ratio 136 to a predefined threshold to determinewhether content 132 (stored on data array 130) should be compressed 310.For example, assume for illustrative purposes that this predefinedthreshold is 3:1, wherein if the compression ratio is less than 3:1,content 132 (stored on data array 130) would not be compressed 310 bydata caching process 10, as the computational expense of compressingcontent 132 (for storage on data array 130) would not be offset by thespace savings achieved. However, if the compression ratio is greaterthan or equal to 3:1, data caching process 10 would compress 310 content132, as the space savings achieved on data array 130 would offset thecomputational expense of compressing content 132.

As discussed above, data array 130 may include second cache system 128.Accordingly, if data caching process 10 compresses 310 content 132 ondata array 130, if data array 130 also includes second cache system 128,compressing 310 content 132 may also include/may alternatively includecompressing 312 any cached copies of content 132 stored on second cachesystem 128.

Uncompressed Data Retrieval:

Data caching process 10 may be configured to minimize/reduce processorloading by intelligently determining whether to decompress cached filesor obtain uncompressed versions of those cached files.

Referring also to FIG. 7, data caching process 10 may be configured toreceive 350 read request 120 on first cache system 126, wherein readrequest 120 identifies previously-written content (e.g., content 132)included within data array 130. Data caching process 10 may determine352 if content 132 (identified in read request 120) is locally storedwithin first cache system 126 in a compressed format (e.g., ascompressed content 132), and if content 132 (identified in read request120) is stored within data array 130 in an uncompressed format (e.g., ascontent 132).

If it is determined 352 that the previously-written content requested inread request 120 is available locally (from first cache system 126) in acompressed format (e.g., compressed content 134) and is availableremotely (from data array 130) in an uncompressed format (e.g., content132), data caching process 10 may determine 354 if it is lesscomputationally expensive to obtain previously-written content requestedin read request 120 from data array 130 in an uncompressed format (e.g.,content 132). Specifically, it may consume considerable processing powerto decompress compressed content. Accordingly, when a compressed copy(e.g., compressed content 134) of the previously-written contentrequested in read request 120 is available locally (e.g. from firstcache system 126) and an uncompressed copy (e.g., content 132) of thepreviously-written content requested in read request 120 is availableremotely (e.g. from data array 130), it may consume less processingpower to obtain the uncompressed copy of the previously-written contentrequested in read request 120 from data array 130 then it would consumeto decompress the compressed copy of the previously-written contentrequested in read request 120 from first cache system 126.

There are many factors that data caching process 10 may take intoconsideration when making determination 354. For example, thecompression ratio (as discussed above) of the compressed content may betaken into consideration when making determination 354, as contenthaving higher compression ratios may be more computationally expensiveto decompress than content having lower compression ratios.Additionally, the current level of network traffic between data array130 and server computer/controller 100 may be taken into consideration,as additional loading of a crowded network may be deemed undesirable bydata caching process 10. Further, the level of loading of theprocessor(s) included within server computer/controller 100 may be takeninto consideration by data caching process 10, as additional loading ofthe processor(s) included within server computer/controller 100 may bedeemed undesirable by data caching process 10. Additionally, the levelof loading of the processor(s) included within data array 130 may betaken into consideration by data caching process 10, as additionalloading of the processor(s) included within data array 130 may be deemedundesirable by data caching process 10

If data caching process 10 determines 354 that it is lesscomputationally expensive to obtain the previously-written contentrequested in read request 120 in an uncompressed format (e.g., content132) from data array 130, data caching process 10 may obtain 356 theuncompressed content (e.g., content 132) stored within data array 130.

If data caching process 10 determines 354 that it is not lesscomputationally expensive to obtain the previously-written contentrequested in read request 120 in an uncompressed format (e.g., content132) from data array 130, data caching process 10 may decompress 358 thecompressed content (e.g., compressed content 134) stored within firstcache system 126.

As discussed above, data array 130 may include second cache system 128.Accordingly, when data caching process 10 determines 352 that thepreviously-written content requested in read request 120 is availablelocally (from first cache system 126) in a compressed format (e.g.,compressed content 134) and is available remotely (from data array 130)in an uncompressed format (e.g., content 132), data caching process 10may also/alternatively determine 360 if the previously-written contentidentified in read request 120 is stored within second cache system 128of data array 130 in an uncompressed format.

Backend Content Copy:

Data caching process 10 may be configured to minimize/reduce networkloading by intelligently determining whether data located in data array130 should be copied from a first location to a second location withindata array 130 (as opposed to being transmitted over networkinfrastructure 114).

Referring also to FIG. 8, data caching process 10 may be configured toreceive 400 write request 116 on first cache system 126, wherein writerequest 116 identifies new content (e.g., content 118) to be written todata array 130.

As discussed above, data write request 116 may include a storage address200 that defines the intended storage location within storage array 130at which content 118 is to be stored. For example, storage address 200may define a particular logical unit within data array 130 (e.g., a LUNor Logical Unit Number) and a particular storage address within thatspecific logical unit (e.g., an LBA or Logical Block Address) forstoring content 118.

As discussed above, a content identifier (e.g., content identifier 256)may be a mathematical representation of a specific piece of content thatmay allow e.g. server computer/controller 100 to quickly determinewhether two pieces of content are identical, as identical pieces ofcontent would have identical content identifiers.

In one particular embodiment, content identifier 256 may be a hashfunction of the content. Upon receiving 400 write request 116 andcontent 118, data caching process 10 may generate 402 content identifier256 for content 118. As discussed above, content identifier 256generated 402 for the content (i.e., content 118) identified withinwrite request 116 may be a hash function (e.g., a cryptographic hash) ofcontent 118.

As is known in the art, a hash function is an algorithm/subroutine thatmaps large data sets to smaller data sets. The values returned by a hashfunction are typically called hash values, hash codes, hash sums,checksums or simply hashes. Hash functions are mostly used to acceleratetable lookup or data comparison tasks such as e.g., finding items in adatabase and detecting duplicated or similar records in a large file.

For example, assume for illustrative purposes that write request 116includes storage address 200 that defines the intended storage locationfor content 118 as LUN0/LBA0. Accordingly, upon receiving 400 writerequest 116, data caching process 10 may generate 402 content identifier256 for content 118. Assume for illustrative purposes that data cachingprocess 10 generates a hash of content 118, resulting in the generation402 of content identifier 256 (namely hash value acdfcla).

This newly-generated content identifier 256 (i.e. acdfcla) associatedwith content 118 may be compared 404 to each of the other contentidentifiers (namely abalabz, alazcha, abalabz, alazcha) included withincontent directory 250 for first cache system 126 to determine if thenewly-generated content identifier 256 (i.e. acdfcla) matches any of theother content identifiers (namely abalabz, alazcha, abalabz, alazcha)included within content directory 250.

As discussed above, each entry of the plurality of entries 252 includedwithin content directory 250 is associated with a unique piece ofcontent included within first cache system 126. Accordingly, each uniquecontent identifier included within content directory 250 may beassociated with a unique piece of content written to first cache system126.

If, when performing comparison 404, data caching process 10 does notidentify a content identifier (i.e., abalabz, alazcha, abalabz, alazcha)within content directory 250 that matches the above-described,newly-generated content identifier (i.e. acdfcla), data caching process10 may write 406 content 118 to first cache system 126 and may provide408 a copy of content 118 to data array 130 for storage within dataarray 130. Additionally, data caching process 10 may modify 410 contentdirectory 250 to include a new entry (i.e., entry 258) that defines thenewly-generated content identifier (i.e. acdfcla), the location ofcontent 118 within first cache system 126 (i.e., 001011), and thelocation of content 118 within data array 130 (i.e., LUN0/LBA0).

If, when performing comparison 404, data caching process 10 identified acontent identifier within content directory 250 that matched theabove-described, newly-generated content identifier (i.e. acdfcla), datacaching process 10 would perform differently.

Accordingly, further assume for illustrative purposes that a secondwrite request (i.e., write request 116′) includes storage address 200′that defines the intended storage location for content 118′ asLUN0/LBA1. Accordingly, upon receiving 400 write request 116′, datacaching process 10 may generate 402 content identifier 256 for content118′. Assume for illustrative purposes that data caching process 10generates a hash of content 118′, resulting in the generation 402 ofcontent identifier 256 (namely hash value alazcha).

This newly-generated content identifier 256 (i.e. alazcha) associatedwith content 118′ may be compared 404 to each of the other contentidentifiers (namely abalabz, alazcha, abalabz, alazcha) included withincontent directory 250 for first cache system 126 to determine if thenewly-generated content identifier 256 (i.e. alazcha) matches any of theother content identifiers (namely abalabz, alazcha, abalabz, alazcha)included within content directory 250.

If, when performing comparison 404, data caching process 10 doesidentify a content identifier (namely alazcha) within content directory250 that matches the above-described, newly-generated content identifier(i.e. alazcha), data caching process 10 may perform a couple offunctions.

For example, data caching process 10 may copy 412 content on data array130 from a first location (namely LUN4/LBA7) on data array 130associated with the matching content identifier to a second location(namely LUN0/LBA1) on data array 130 associated with the newly-generatedcontent identifier. Specifically and for the reasons discussed above,since data caching process 10 identified matching content identifiers(i.e., having the same value of alazcha), content 118′ must be identicalto the content stored at LUN4/LBA7. Accordingly, instead of transmittingcontent 118′ from server computer/controller 100 to data array 130, datacaching process 10 may simply effectuate on data array 130 a copy of thedata currently stored at LUN4/LBA7 to LUN0/LBA1, thus freeing up servercomputer/controller 100 to perform other functions and reducing networktraffic on network infrastructure 114.

Further, data caching process 10 may modify 414 the entry (i.e., entry260) within content directory 250 that is associated with the matchingcontent identifier (i.e., alazcha) to include storage address 200′ thatdefines the intended storage location for content 118′ (i.e., LUN0/LBA1within data array 130), thus generating modified entry 260′.Accordingly, modified entry 260 identifies that the pieces of contentthat are currently stored at LUN4/LBA7 and LUN0/LBA1 within data array130 are identical. Accordingly, a single piece of cached content(located first cache address 010111 within first cache system 126) maybe used as a local cached copy for both pieces of content stored on dataarray 130.

Content Identifier Backend Retrieval:

Data caching process 10 may be configured to minimize/reduce loading ofserver computer/controller 100 by determining if content already existson first cache system 126 before retrieving the same from data array130.

Referring also to FIG. 9, data caching system 10 may be configured toreceive 450 read request 120 on first cache system 126, wherein readrequest 120 identifies previously-written content (e.g., content 132)included within data array 130. Upon receiving 450 read request 120,data caching process 10 may process read request 120 to determine ifcontent 132 is locally available within first cache system 126.

As discussed above, read request 120 may define a particular logicalunit within data array 130 (e.g., a LUN or Logical Unit Number) and aparticular storage address within that specific logical unit (e.g., anLBA or Logical Block Address) for retrieving content 132 sought fromdata array 130.

As discussed above, content directory 250 may include plurality ofentries 252, wherein each of these entries may identify: data arraystorage address 200/202 (e.g. a logical storage unit and a storageaddress at which a specific piece of previously-written content islocated within storage array 130); first cache address 254 (e.g., thelocation within first cache system 126 at which the specific piece ofpreviously-written content is also located), and content identifier 256for the specific piece of previously-written content.

Accordingly, when data caching process 10 processes read request 120 todetermine if content 132 is available within first cache system 126,data caching process 10 may review content directory 250 to see if theLUN and LBA defined within read request 120 is listed within contentdirectory 250.

Assume for illustrative purposes that read request 120 is requesting thedata stored at LUN6/LBA4 of data array 130. As LUN6/LBA4 is not listedas a data array storage address 200/202 within content directory 250,data caching process 10 will determine that the content requested inread request 120 is not available locally (i.e. from first cache system126).

Accordingly, data caching process 10 may request 452, from the dataarray, the content identifier for the content identified in the readrequest (namely content 132). Upon receiving request 452 from datacaching process 10, data array 130 may either a) retrieve the contentidentifier for the content identified in read request 120 (if previouslygenerated and stored within e.g. a content directory (not shown) forsecond cache system 128; or b) generate the content identifier for thecontent identified in the read request 120 (as data array 130 has accessto content 132). Once generated/retrieved by data array 130, contentidentifier 138 may be received 454 by data caching process 10 from dataarray 130. As discussed above, content identifier 138 may be a hashfunction of the content requested in data request 120 (namely content132).

Data caching process 10 may compare 456 content identifier 138 (i.e.,the content identifier associated with the content identified withinread request 120, namely content 132) to each of the content identifiers(namely abalabz, alazcha, abalabz, alazcha) included within contentdirectory 250 for first cache system 126 to determine if a matchingcontent identifier exists. As discussed above, each of the plurality ofcontent identifiers (namely abalabz, alazcha, abalabz, alazcha) includedwithin content directory 250 is associated with a piece of contentpreviously-written to first cache system 126.

If, when performing comparison 456, data caching process 10 does notidentify a content identifier included within content directory 250 thatmatches content identifier 138, data caching process 10 may obtain 458the previously-written content identified in read request 120 (i.e.,content 132) from data array 130 and may write 460 content 132 to firstcache system 126 (at e.g., first cache address 111011). Additionally,data caching process 10 may modify 462 content directory 250 to includea new entry (i.e., entry 262) that defines content identifier 138(namely ablcboa), the location of content 132 within first cache system126 (i.e., first cache address 111011), and the location of content 132within data array 130 (i.e., LUN6/LBA4).

If, when performing comparison 456, data caching process 10 identifies acontent identifier (either abalabz, alazcha, abalabz or alazcha)included within content directory 250 that matches content identifier138, data caching process 10 may retrieve 464 content 132 identified inread request 120 from first cache system 126.

Further, data caching process 10 may also modify 466 an entry withincontent directory 250 that is associated with the matching contentidentifier to include a storage address that defines the storagelocation of content 132 (i.e., LUN6/LBA4 within data array 130). Thismodification of a data entry within content directory 250 would besimilar to the manner in which entry 260 was modified to create modifiedentry 260′.

For example, assume that the matching content identifier was againalazcha which was included within entry 260. Accordingly, entry 260would be modified to also identify the content stored at LUN6/LBA4(i.e., content 132) in addition to the content stored at LUN4/LBA7, asthe content at LUN6/LBA4 and LUN4/LBA7 within data array 130 areidentical. Accordingly, a single piece of cached content within firstcache system 126 may be used as a local cached copy for both pieces ofcontent stored on data array 130.

Content Identifier Generation

Data caching process 10 may be configured to conserve storage space ondata array 130 by deleting redundant data.

Referring also to FIG. 10, data caching process 10 may be configured toreceive 500 read request 120 on first cache system 126, wherein readrequest 120 identifies previously-written content (e.g., content 132)included within data array 130. Upon receiving 450 read request 120,data caching process 10 may process read request 120 to determine ifcontent 132 is locally available within first cache system 126.

As discussed above, read request 120 may define a particular logicalunit within data array 130 (e.g., a LUN or Logical Unit Number) and aparticular storage address within that specific logical unit (e.g., anLBA or Logical Block Address) for retrieving content 132 sought fromdata array 130.

As discussed above, content directory 250 may include plurality ofentries 252, wherein each of these entries may identify: data arraystorage address 200/202 (e.g. a logical storage unit and a storageaddress at which a specific piece of previously-written content islocated within storage array 130); first cache address 254 (e.g., thelocation within first cache system 126 at which the specific piece ofpreviously-written content is also located), and content identifier 256for the specific piece of previously-written content.

Accordingly, when data caching process 10 processes read request 120 todetermine if content 132 is available within first cache system 126,data caching process may review content directory 250 to see if the LUNand LBA defined within read request 120 is listed within contentdirectory 250.

Assume again for illustrative purposes that read request 120 isrequesting the data stored at LUN6/LBA4 of data array 130. As LUN6/LBA4is not listed as a data array storage address 200/202 within contentdirectory 250, data caching process 10 will determine that the contentrequested in read request 120 is not available locally (i.e. from firstcache system 126).

Accordingly, data caching process 10 may need to obtain 502 content 132identified in read request 120 from data array 130. In this particularexample, since LUN6/LBA4 is not defined within content directory 250, alocal cached copy of content 132 is not present/available within firstcache system 126 and data caching process 10 will need to obtain 502content 132 from data array 130.

Once content 132 is obtained 502 from data array 130, data cachingprocess 10 may generate 504 a content identifier (e.g., contentidentifier 138) for content 132. As discussed above, content identifier138 generated 504 for the content 132 identified within read request 120may be a hash function of content 132. Assume for illustrative purposesthat data caching process 10 generates a hash of content 132, resultingin the generation 504 of content identifier 138 (namely hash valueablcboa).

Data caching process 10 may compare 506 content identifier 138 (i.e.,the content identifier associated with the content identified withinread request 120, namely content 132) to each of the content identifiers(e.g., abalabz, alazcha, abalabz, alazcha) included within contentdirectory 250 for first cache system 126 to determine if a matchingcontent identifier exists. As discussed above, each of the plurality ofcontent identifiers (namely abalabz, alazcha, abalabz, alazcha) includedwithin content directory 250 is associated with a piece of contentpreviously-written to first cache system 126.

If, when performing comparison 506, data caching process 10 does notidentify a content identifier included within content directory 250 thatmatches content identifier 138, data caching process 10 may write 508content 132 to first cache system 126 (at e.g., first cache address111011). Additionally, data caching process 10 may modify 510 contentdirectory 250 to include a new entry (i.e., entry 262) that definescontent identifier 138 (namely ablcboa), the location of content 132within first cache system 126 (i.e., first cache address 111011), andthe location of content 132 within data array 130 (i.e., LUN6/LBA4).

If, when performing comparison 456, data caching process 10 identifies acontent identifier (either abalabz, alazcha, abalabz or alazcha)included within content directory 250 that matches content identifier138, data caching process 10 may modify 512 an entry within contentdirectory 250 that is associated with the matching content identifier toinclude a storage address that defines the storage location of content132 (i.e., LUN6/LBA4 within data array 130). This modification of a dataentry within content directory 250 would be similar to the manner inwhich entry 260 was modified to create modified entry 260′.

Assume for illustrative purposes that data caching process 10 generatesa hash of content 132, resulting in the generation 504 of contentidentifier 138 having a hash value of ablcboa. As the matching contentidentifier is included within entry 260 of content directory 250, entry260 may be modified 512 by data caching process 10 to also identify thepiece of content stored at LUN6/LBA4 (i.e., content 132) in addition tothe piece of content stored at LUN4/LBA7, as the content at LUN6/LBA4and LUN4/LBA7 within data array 130 are identical.

Additionally, if a matching content identifier is identified, datacaching process 10 may notify 514 data array 130 that content 130identified in read request 120 is identical to the previously-writtencontent associated with the matching content identifier. Accordingly andin this example, content 130 stored at LUN6/LBA4 within data array 130is identical to the content stored at LUN4/LBA7 within data array 130.Once notified 516, data array 130 may e.g., delete one of the redundantcopies (e.g., at LUN6/LBA4 or LUN4/LBA7) on e.g., non-volatile,electro-mechanical memory system 112 and/or second cache system 128 andmay map LUN6/LBA4 and LUN4/LBA7 to a single memory location within e.g.,non-volatile, electro-mechanical memory system 112 and/or second cachesystem 128.

As will be appreciated by one skilled in the art, the present disclosuremay be embodied as a method, system, or computer program product.Accordingly, the present disclosure may take the form of an entirelyhardware embodiment, an entirely software embodiment (includingfirmware, resident software, micro-code, etc.) or an embodimentcombining software and hardware aspects that may all generally bereferred to herein as a “circuit,” “module” or “system.” Furthermore,the present disclosure may take the form of a computer program producton a computer-usable storage medium having computer-usable program codeembodied in the medium.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods and computer program products according to variousembodiments of the present disclosure. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof code, which comprises one or more executable instructions forimplementing the specified logical function(s). It should also be notedthat, in some alternative implementations, the functions noted in theblock may occur out of the order noted in the figures. For example, twoblocks shown in succession may, in fact, be executed substantiallyconcurrently, or the blocks may sometimes be executed in the reverseorder, depending upon the functionality involved. It will also be notedthat each block of the block diagrams and/or flowchart illustration, andcombinations of blocks in the block diagrams and/or flowchartillustration, can be implemented by special purpose hardware-basedsystems that perform the specified functions or acts, or combinations ofspecial purpose hardware and computer instructions.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of the disclosure.As used herein, the singular forms “a”, “an” and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. It will be further understood that the terms “comprises”and/or “comprising,” when used in this specification, specify thepresence of stated features, integers, steps, operations, elements,and/or components, but do not preclude the presence or addition of oneor more other features, integers, steps, operations, elements,components, and/or groups thereof.

The corresponding structures, materials, acts, and equivalents of allmeans or step plus function elements in the claims below are intended toinclude any structure, material, or act for performing the function incombination with other claimed elements as specifically claimed. Thedescription of the present disclosure has been presented for purposes ofillustration and description, but is not intended to be exhaustive orlimited to the disclosure in the form disclosed. Many modifications andvariations will be apparent to those of ordinary skill in the artwithout departing from the scope and spirit of the disclosure. Theembodiment was chosen and described in order to best explain theprinciples of the disclosure and the practical application, and toenable others of ordinary skill in the art to understand the disclosurefor various embodiments with various modifications as are suited to theparticular use contemplated.

A number of implementations have been described. Having thus describedthe disclosure of the present application in detail and by reference toembodiments thereof, it will be apparent that modifications andvariations are possible without departing from the scope of thedisclosure defined in the appended claims.

What is claimed is:
 1. A computer-implemented method of processing writerequests comprising: receiving a write request on a first cache system,wherein the write request identifies new content to be written to a dataarray, wherein the data array is remotely connected via a network to thefirst cache system; comparing a write request content identifierassociated with the new content to a plurality of content identifiersincluded within a content directory for the first cache system todetermine if a matching content identifier exists, wherein each of theplurality of content identifiers is associated with a piece ofpreviously-written content included within the first cache system; if amatching content identifier is identified, copying content on the dataarray from a first location on the data array associated with thematching content identifier to a second location on the data arrayassociated with the write request content identifier, wherein thecontent on the data array is copied from the first location on the dataarray to the second location on the data array without transmitting thenew content to the data array via the network.
 2. Thecomputer-implemented method of claim 1 further comprising: if a matchingcontent identifier is not identified: writing the new content to thefirst cache system; modifying the content directory to include the writerequest content identifier; and providing the new content to the dataarray.
 3. The computer-implemented method of claim 1 further comprising:generating the write request content identifier for the new content. 4.The computer-implemented method of claim 3 wherein the write requestcontent identifier is a hash function of the new content to be writtento the data array.
 5. The computer-implemented method of claim 1 whereinthe write request identifies a logical unit and a storage address forstoring the new content within the data array.
 6. Thecomputer-implemented method of claim 5 further comprising: if a matchingcontent identifier is identified, modifying an entry within the contentdirectory that is associated with the matching content identifier toidentify the logical storage unit and the storage address for storingthe new content within the data array.
 7. The computer-implementedmethod of claim 1 wherein the content directory for the first cachesystem includes a plurality of entries, wherein each of the plurality ofentries is associated with a specific piece of previously-writtencontent within the first cache system, wherein each of the plurality ofentries within the content directory identifies: a logical storage unitand a storage address at which the specific piece of previously-writtencontent is located within the storage array; a first cache address atwhich the specific piece of previously-written content is located withinthe first cache system, and a content identifier for the specific pieceof previously-written content.
 8. A computer program product residing ona non-transitory computer readable medium having a plurality ofinstructions stored thereon which, when executed by a processor, causethe processor to perform operations comprising: receiving a writerequest on a first cache system, wherein the write request identifiesnew content to be written to a data array, wherein the data array isremotely connected via a network to the first cache system; comparing awrite request content identifier associated with the new content to aplurality of content identifiers included within a content directory forthe first cache system to determine if a matching content identifierexists, wherein each of the plurality of content identifiers isassociated with a piece of previously-written content included withinthe first cache system; if a matching content identifier is identified,copying content on the data array from a first location on the dataarray associated with the matching content identifier to a secondlocation on the data array associated with the write request contentidentifier, wherein the content on the data array is copied from thefirst location on the data array to the second location on the dataarray without transmitting the new content to the data array via thenetwork.
 9. The computer program product of claim 8 further comprisinginstructions for: if a matching content identifier is not identified:writing the new content to the first cache system; modifying the contentdirectory to include the write request content identifier; and providingthe new content to the data array.
 10. The computer program product ofclaim 8 further comprising instructions for: generating the writerequest content identifier for the new content.
 11. The computer programproduct of claim 10 wherein the write request content identifier is ahash function of the new content to be written to the data array. 12.The computer program product of claim 8 wherein the write requestidentifies a logical unit and a storage address for storing the newcontent within the data array.
 13. The computer program product of claim12 further comprising instructions for: if a matching content identifieris identified, modifying an entry within the content directory that isassociated with the matching content identifier to identify the logicalstorage unit and the storage address for storing the new content withinthe data array.
 14. The computer program product of claim 8 wherein thecontent directory for the first cache system includes a plurality ofentries, wherein each of the plurality of entries is associated with aspecific piece of previously-written content within the first cachesystem, wherein each of the plurality of entries within the contentdirectory identifies: a logical storage unit and a storage address atwhich the specific piece of previously-written content is located withinthe storage array; a first cache address at which the specific piece ofpreviously-written content is located within the first cache system, anda content identifier for the specific piece of previously-writtencontent.
 15. A computing system including at least one processor and atleast one memory architecture coupled with the at least one processor,wherein the computing system is configured to perform operationscomprising: receiving a write request on a first cache system, whereinthe write request identifies new content to be written to a data array,wherein the data array is remotely connected via a network to the firstcache system; comparing a write request content identifier associatedwith the new content to a plurality of content identifiers includedwithin a content directory for the first cache system to determine if amatching content identifier exists, wherein each of the plurality ofcontent identifiers is associated with a piece of previously-writtencontent included within the first cache system; if a matching contentidentifier is identified, copying content on the data array from a firstlocation on the data array associated with the matching contentidentifier to a second location on the data array associated with thewrite request content identifier, wherein the content on the data arrayis copied from the first location on the data array to the secondlocation on the data array without transmitting the new content to thedata array via the network.
 16. The computing system of claim 15 furtherconfigured to perform operations comprising: if a matching contentidentifier is not identified: writing the new content to the first cachesystem; modifying the content directory to include the write requestcontent identifier; and providing the new content to the data array. 17.The computing system of claim 15 further configured to performoperations comprising: generating the write request content identifierfor the new content.
 18. The computing system of claim 17 wherein thewrite request content identifier is a hash function of the new contentto be written to the data array.
 19. The computing system of claim 15wherein the write request identifies a logical unit and a storageaddress for storing the new content within the data array.
 20. Thecomputing system of claim 19 further configured to perform operationscomprising: if a matching content identifier is identified, modifying anentry within the content directory that is associated with the matchingcontent identifier to identify the logical storage unit and the storageaddress for storing the new content within the data array.
 21. Thecomputing system of claim 15 wherein the content directory for the firstcache system includes a plurality of entries, wherein each of theplurality of entries is associated with a specific piece ofpreviously-written content within the first cache system, wherein eachof the plurality of entries within the content directory identifies: alogical storage unit and a storage address at which the specific pieceof previously-written content is located within the storage array; afirst cache address at which the specific piece of previously-writtencontent is located within the first cache system, and a contentidentifier for the specific piece of previously-written content.